pp108 : Modeling an Email for a Business Event Response

Modeling an Email for a Business Event Response

This topic describes the procedure to model an Email, which can be triggered as one of the actions in case the specified Business Event Response and condition meet.

The objective of the Model Email is to send the process and related contextual information to the user, when a specified condition based on a Business Event Response is met.

In an Email, you can include the information relevant to the business process, user, and the required response of external Web services, and so on. You can customize the contents of the email template as per the requirement in terms of the background color, font size, formatting and so on as per the requirement.

The components of the Email can be modeled by changing the HTML code. The Attributes related to the Business Event Response such as Process attributes and Contextual attributes would be available in the 'Message' area under the Message data tree of the Email template. These attributes can be used in any of the above components by dropping them in the specific area.

  1. In the Email model page, under the Email Model of the Model Components section, provide the necessary message, which has to be sent as part of the email. The Model has Header, Salutation, Body, Signature, Footer, and Application Details components. The selected attributes in the earlier stages are available under the Message section of the Email template. These attributes can be used in any of Model components by dropping them in the specific area.
  2. Enter the Recipient's name and Email id in the Recipient's Name and Email Id fields. The Email template, defined by you, would be made available as a Web service. It can be triggered as an action, in the form of invoking Web service. The created Email template is available as a Web service in the Custom Space, which is available in the current user organization with the name of the Business Event Response.

    Note:
    For more information on the modeling the email template, refer to Creating an E-mail Model.

  3. Select any one of the Web service Definition Set option under Select Web service Definition Set section, as the Email template defined by you would be available as Web service :

    Option

    Action

    New

    Select New option, if you want to provide a new Web service Definition Set to the Business Event Response. This option is selected by default. The Web service Definition Set Name and Web service Definition Set Namespace fields are enabled; enter a name and namespace in the respective fields. By default, it gets filled by the Business Event Response name.

    Note: The Web service Definition Set Name, Web service Definition Set Namespace and Webservice Interface are mandatory fields and should not begin with a number. Blank spaces or special characters are not allowed.

    Existing

    Select Existing option, if you want to apply any existing Web service Definition Set. The Existing Web service Definition Set Name field is enabled with .

    Note: The Existing Web service Definition Set Name is a mandatory field and it should not begin with a number. Blank spaces or special characters are not allowed.


    Click , and select the Web service definition set name from the Select Web service Definition Set dialog. The Existing Web service Definition Set Namespace field remains disabled. Depending on the Web service Definition Set you select, this field is populated with Namespace automatically. Select a Webservice Interface from Select Web service Interface drop-down.

    BAM Default

    Select BAM Default option to select the default Web service Definition Set. The Webservice Definition Set Namespace is filled automatically.

    Note:
    Email Web service thus created can be used as an action, in the form of invoking Web service.

After you complete this task:
Click Next to define actions on the build rules (conditions) and define actions page.


Related tasks

Selecting Business Process Events
Selecting Business Process Event Attributes
Selecting Contextual Information